Seamless wireless mobility

ABSTRACT

Seamless wireless mobility is described. In one embodiment, a mobility manager can query a subscriber catalog for a current registration status of handset. The mobility manager can then use the registration status to send a first signal to the handset over either a wireless network or an Internet protocol-based network.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.12/538,465, now U.S. Pat. No. 7,720,040, filed Aug. 10, 2009 and issuedon May 18, 2010, which is a continuation of U.S. patent application Ser.No. 11/275,783, now U.S. Pat. No. 7,574,207, filed Jan. 27, 2006 andissued on Aug. 11, 2009, both of which are hereby incorporated byreference in their entirety.

BACKGROUND

Given their portable nature and ease of use, wireless handsets (such ascellular phones) have enjoyed wide proliferation. This is especially thecase among users who move around frequently, but wish to stay in contactwith their work colleagues, families and other individuals or entitiesof importance.

Often, however, coverage problems arise when a user attempts to use ahandset inside of a building. For example, many electromagnetic signals(such as radio frequencies used by Wi-Fi devices and cellphones) areunable to fully propagate through walls, metalized glass or other commonbuilding materials which separate the inside of a building from anoutside environment. As a result, the user may experience a degradationof service or may be precluded entirely from sending or receivinginformation from their handset to an existing outside network.

Additionally, many wireless handset users also have other communicationdevices, such as “soft phones” using voice over IP (VoIP) protocols, aswell as analog phones communicating over POTS (plain old telephonesystem) lines for both business and personal use. Thus a single user maybe associated with several different telephone numbers receive callsover a variety of different transmission mediums.

SUMMARY

This summary is provided to introduce simplified concepts of seamlesswireless mobility, which is further described below in the DetailedDescription. This summary is not intended to identify essential featuresof the claimed subject matter, nor is it intended for use in determiningthe scope of the claimed subject matter. In one embodiment of seamlesswireless mobility, a mobility manager can query a subscriber catalog fora current registration status of a handset. The mobility manager can tenuse the registration status to send a first signal to the handset overeither a wireless network or an Internet protocol-based network.

According to one embodiment, a status of registration of a handset isestablished by determining if the handset is registered to a wirelessnetwork or an access point. This status of registration can be used tosend a signal to the handset. For example, if the handset is registeredon an access point, the signal can be sent over a network to which theaccess point is coupled using, for example, Internet protocol (IP).Alternately, if the handset is registered to the wireless network, thesignal may be sent to the handset over the wireless network. In anotherembodiment of seamless wireless mobility, if the handset is registeredon the access point, the handset can be rung in response to signalsaddressed to other phones associated with the access point (such as IPphones).

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items.

FIG. 1. is a block diagram illustrating an exemplary environmentincluding a handset, a wireless network, an Internet protocol multimediasubsystem, and a location in which an access point may be found.

FIG. 2 is a block diagram illustrating an exemplary telephony featureserver on which a mobility manager may reside.

FIG. 3 is a flow diagram illustrating a exemplary method of sending asignal to a handset.

FIG. 4 is a flow diagram illustrating a exemplary method of sending asignal to a handset and at least one other phone when the handset isregistered on an access point.

FIG. 5 is a flow diagram illustrating another exemplary method ofsending a signal to a handset and at least one other phone when thehandset is registered on an access point.

FIG. 6 is a flow diagram illustrating an exemplary method of sending asignal from a handset.

DETAILED DESCRIPTION Environment

FIG. 1 shows an exemplary environment 100 in which the techniquesdescribed herein can be implemented. Environment 100 includes a wirelesshandset 102, a wireless network 104, an Internet protocol multimediasubsystem (IMS) 106 and a location 108. In but one possibleimplementation described herein, the handset 102 is a dual mode cellphone capable of communicating with the wireless network 104 and anaccess point 110 in location 108. However, the handset 102 could also beany of a variety of other types of computer and computer-like deviceshaving the capability of communicating with (1) wireless network 104including, for example, a Global System for Mobile Communications (GSM)network or Universal Mobile telecommunications System (UMTS) network,and (2) access point 110 using wired and wireless technologiesincluding, for example, the IEEE 802.11b wireless networking standard(Wi-Fi). Such devices may include a tablet PCT, a personal digitalassistant (PDA), or a handheld video gaming device. It will also beunderstood that a plurality of handsets 102 could be found, and utilizedsuccessfully in, environment 100.

According to an exemplary embodiment, a wireless handset, such ashandset 102, may have varied functionality allowing a user to performmany different tasks. For example, in addition to sending and receivingvoice-based communications, a user may also be able to use handset 102to run a host of standard computer programs (word processing,spreadsheets, etc.) and games, send and receive emails, browse theInternet, etc.

Internet protocol multimedia subsystem (IMS) 106 can allow for seamlesswireless mobility of the handset 102 between the wireless network 104and the location 108. As the handset 102 moves into an effectivecommunication range of access point 110, IMS 106 can effect a handoverof the handset 102 from wireless network 104 to access point 110. Asdiscussed in more detail below, the IMS 106 can do this by collectingand/or observing registration information regarding the handset 102. Forexample, when the handset is within a range in which the handset 102 caneffectively communicate with access point 110, the registration of thehandset 102 may be removed from wireless network 104 (and cell tower 112over which handset 102 may be accessing wireless network 104), andhandset 102 can be registered on access point 110. The IMS 106 candetect this registration status and begin allowing handset 102 to sendand receive signals via access point 110. Access point 110 can send andreceive these signals over a network 114, which can include an IP-basednetwork, including, e.g., and IP WAN or the Internet. When handset 102is communicating with access point 110 through wireless technologies, auser may not even be aware that the handoff from wireless network 104 toaccess point 110 and the network 114 has taken place.

Access point 110 may include any device or architecture allowing handset102 to send or receive data over network 114. Access point 110 maybenefit from a small size—including dimensions less than or equal tothose of a WiFi access point. As a result, access point 110 can fiteasily and unobtrusively in a building environment.

Access point 110 may also be very simple to use. For example, asmentioned above, the small size of access point 110 can made accesspoint 110 easy to install by end users. Moreover, access point 110 mayalso be able to self-configure itself by examining its environment,noting the presence of competing macro-cells, such as cell tower 112,and other access points 110, and noting the presence of handsets 102.

Moreover, since access point 110 may be able to recognize all of thedownlink channels in use around it from other devices, including macrocells, access point 110 may be able to choose an appropriate channelthat handset 102 is able to support. Access point 110 may communicatedirectly with handset 102 and command handset 102 to change itself to anappropriate channel (and power level) to communicate with access point110, such that a high level of quality of communication between handset102 and access point 110 can be achieved and maintained.

It will be understood that the elements discussed above with regard tothe access point 110 may be implemented by software, hardware or acombination thereof. Moreover, security functions, such as determiningser privilege to enter a cellular carrier's network, or defensivemechanisms against the passing of viruses, may exist in access point110, wireless network 104 or any point between these elements.

As shown in FIG. 1, access point 110 may be placed in location 108.Location 108 may include any environment in which it may be desirable touse handset 102 to send and/or receive data over a network, such asnetwork 114. This may include a home environment, such as a family roomor bedroom. Alternately, location 108 may include a businessenvironment, such as an office, or a common space in proximity of one ormore offices. Similarly, location 108 could include a public space, suchas a hospital, restaurant or coffee shop offering Wi-Fi access to itscustomers. In addition, location 108 could be outside of a building,such as in a public park. In yet another possible implementation,location 108 could include underground facilities, and any otherlocations where reception and transmission of wireless signals to andfrom a wireless network is problematic. For example, in elevators, wherewireless communications with the outside environment are often prone todisruption, access point 110 could be placed in the elevator shaft. Insuch a configuration the shaft could act as a wave guide, allowing highquality communication between access point 110 and handset(s) 102traveling up and down the shaft in the elevator(s).

Regardless of where location 108 might be, several different devices canbe associated with the access point 110. For example, a computer 116 mayaccess network 114 via access point 110 through wired or wireless means.Additionally, an IP phone 118 could be coupled to access point 110through wired or wireless means and send and receive data over network114 via the access point. Similarly, an analog phone 120 could becoupled to access point 110 through an analog terminal adapter 122 andwired or wireless means, enabling analog phone 120 to act like an IPphone. Other devices, which are not shown for the sake of graphicclarity, could also be coupled through wired or wireless means to accesspoint 110, including game consoles, personal digital assistants, tabletPCs, etc. It will also be understood that additional communicationsdevices, such as analog telephones coupled to plain old telephone system(POTS) lines, may be found in location 108 and may be consideredassociated with access point 110 if so desired by a user.

In operation, when handset 102 is out of range of access point 110—andthus cannot communicate with access point 110 at an acceptable level ofquality—handset 102 can behave as a normal cellular phone andcommunicate through wireless network 104. For example, if handset 102 iswithin range of cell tower 112, handset 102 can communicate wirelesswith tower 112, thus accessing wireless network 104. In such aninstance, handset 102 will not be registered on access point 110, butwill instead be registered on wireless network 104 as communicatingthrough, for example, a base station controller (BSC) 124 in wirelessnetwork 104. Data being sent and received by handset 102 may betransmitted between BSC 124 and a gateway mobile switching center (GMSC)126 in wireless network 104, via a mobile switching center (MSC) 128.Additionally, information regarding handset 102, including dataindicating on which mobile switching center 128 the handset isregistered, may be stored in a subscriber catalog 129, such as might beassociated with a home locator register (HLR) 130.

If handset 102 is moved closer to location 108, however, and handset 102is placed at a distance from access point 110 where handset 102 andaccess point 110 may communicate through wired or wireless means with anacceptable level of quality, handset 102 may be handed off from celltower 112 to access point 110. In such an instance, handset 102 maycommunicate with access point 110 and uplink signals from handset 102may be received by access point 110 and be transmitted over network 114,to network controller 132 such as an unlicensed mobile access (UMA)network controller. It will be understood that terms ‘signals’ and‘uplink signals’ as used herein may include data and commands sent inanalog or digital form. Thus, ‘signals’ and ‘uplink signals’ may includetext messages, voice transmissions, computer-readable instructions, etc.

Returning to the instant example, transmission of the uplink signalsover network 114 may be conducted utilizing the UMA protocol or anyother protocol in which the signals may be transmitted via an Internetsecurity protocol (IPSEC) tunnel to network controller 132.

At network controller 132, encoded information received over the IPSECtunnel is converted into an interface protocol, such as the cellular Ainterface protocol, and the information may then be transmitted over acoupling to a mobile switching center, such as mobile switching center128. In addition, network controller 132 may also be able to supportmultiple devices having ISPEC tunnel compatible clients (such as UMAclients). In this way network controller 132 can distribute commands,instructions and data addresses to several different devices based onidentities of the devices as designated by the ISPEC tunnel compatibleclients the devices contain.

Once the signals are sent from network controller 132, they may bereceived in mobile switching center 128, from which the signals may thenbe communicated, for example, to a public switched telephone network(PSTN) 134, where they may then be transmitted to any network in theworld. Alternately, the signals may be transmitted from the mobileswitching center 128 to a media gateway (MGW) such MGW 136 in IMS 106,where the signals may then be coupled to a network 114 such as theInternet.

In the other direction, when handset 102 is registered on access point110, once signals intended for handset 102 are received at mobileswitching center 128 from either media gateway 136 or PSTN 134, areverse path is followed. For example, the signals are transmitted frommobile switching center 128 to network controller 132 where the signalsare converted from on interface protocol, such as the cellular Ainterface protocol, to a protocol in which the signals may betransmitted over IPSEC tunnel to the access point 110 (such as the UMAprotocol). Network controller 132 may be able to route the signals tohandset 102 through the location and identification of a client (such asan UMA client) in access point 110 with which handset 102 iscommunicating.

Once the correct access point 110 is located, network controller 132 maytransmit the signals over network 114 to access point 110, where thesignals may be downlinked from access point 10 to handset 102 using, forexample, radio waves, including Wi-Fi frequencies.

Access point 110 may also receive commands and instructions from IMS106. These commands may be sent to access point 110 from IMS 106 over awired or wireless connection (not shown for sake of graphic clarity),and/or a network (such as network 114 illustrated in FIG. 1). Inaddition, information regarding access point 110, and handset 102 may becollected by IMS 106 over the connection, and/or network 114 and storedin a subscriber catalog 137, such as might be associated with homesubscription subsystem (HSS) 138. This information can include theregistration status of handset 102, including if handset 102 isregistered on access point 110 or on a baste station controller such asBSC 124. Additionally, home subscription subsystem 138 can be coupled tohome location register 130, and information can be shared between thetwo. Similarly, home subscription subsystem 138 can sync itselfperiodically, and/or on command, with home location register 130 toupdate the information in home subscription subsystem 138 based on theinformation in home location register 130.

In one implementation, IMS 106 may allow an entity to deduce thegeographic location of access point 110 through examination of thechannels transmitted from adjacent cell towers which access point 110 isable to sense. In yet other implementations, IMS 106 may be able to shutdown access point 110, or allow software updates to be downloaded toaccess point 110.

By utilizing access point 110, a user of handset 102 may be afforded adependable, high-quality connection to wireless network 104. Incontrast, without access point 110, the user would have to rely ondirect communication between handset 102 and an available macro-cell(such as represented by cell tower 112). In such a scenario, deprecationof signal transmission quality or total failure to achieve communicationbetween handset 102 and the macro-cell could result from (1)interference to the propagation of electromagnetic signals posed by thewalls, windows and other obstructions placed by location 108 betweenhandset 102 and tower 112; as well as (2) propagation difficulties posedby the distance between tower 112 and handset 102.

Moreover, it will be understood that even though only one access point110 is illustrated in location 108, a plurality of access point could beemployed in various locations throughout location 108. In this manner,seamless, high quality signal transmission between handset 102 and thenetworks of various cellular and other providers could be ensured inparticular areas of location 108, or if desired, throughout the entirearea of location 108.

It will be understood that communications between, for example, wirelessnetwork 104, and IMS 106, as well as communications between PSTN 134 andIMS 106 may be transmitted via one or more network controllers 140 inIMS 106. Moreover, communications between various elements in IMS 106may be conducted via an IMS core platform (IMS CP) 142, usingtechnologies such as call state control function and media gatewaycontrol function. Also, IMS 106 may include a voicemail feature server(VFS) 144 to accept signals intended for handset 102 when handset 102 isregistered on neither wireless network 104 nor access point 108, or whena user does not answer handset 102 when it is rung in response to anincoming signal.

Recognition of a registration of handset 102, and use of theregistration status to send signals to handset 102 over either wirelessnetwork 104 or network 114 can be made by a telephony feature server(TFS) 146 in IMS 106 on which a mobility manager 148 may reside.

Telephony Feature Server

FIG. 2 illustrates exemplary functional components of telephony featureserver (TFS) 146 which allow TFS 146 to send signals to and from handset102 via either wireless network 104 or network 114. These components mayinclude one or more processor(s) 202, one or more network interface(s)204, and a memory 206. Memory 206 can store programs executed on theprocessor(s) 202 and data generated ruing their execution. Memory 206can also include various computer-readable storage media, such asvolatile media, non-volatile media, removable media, and non-removablemedia. It will be understood that volatile memory may include media suchas random access memory (RAM), and non volatile memory may include readonly memory (ROM). Telephony feature server 146 may also include otherremovable/non-removable, volatile/non-volatile computer storage mediasuch as a hard disk drive for reading from and writing to anon-removable, non-volatile magnetic media, a magnetic disk drive forreading from and writing to a removable, non-volatile magnetic disk(e.g., a “floppy disk”), and an optical disk drive for reading fromand/or writing to a removable, non-volatile optical disk such as aCD-Rom, DVD-Rom, or other optical media. The disk drives and theirassociated computer-readable media can provide non-volatile storage ofcomputer readable instructions, data structures, program modules, andother data for telephony feature server 146.

In addition to including a hard disk, a removable magnetic disk, and aremovable optical disk, as discussed above, memory 206 may also includeother types of computer-readable media capable of storing data that isaccessible by a computer, such as magnetic cassettes or other magneticstorage devices, flash memory cards, electrically erasable programmableread-only memory (EEPROM), and the like. The hard disk drive, magneticdisk drive, and optical disk drive may each be connected to a system busby one or more data media interfaces. Alternatively, the hard diskdrive, magnetic disk drive 108, and optical disk drive 108 may beconnected to the system bus by one or more interfaces.

Any number of programs, program modules, data objects, or other datastructures may be stored on the memory 206 including an operatingsystem, one or more application programs, other program modules, andprogram data.

In this example, memory 206 stores a mobility manager application 148,which when executed on processor(s) 202, allows TFS 146 to determine theregistration status of handset 102, and send signals to and from handset102 over either network 114 or wireless network 104. It will also beunderstood that the name “mobility manager” has been chosen for the sakeof convenience of reference, and not for the sake of limitation. It willalso be understood that mobility manager 148 need not necessarily residein memory 206, and could reside in a memory location coupled to TFS 146.For example, on one implementation, mobility manager 148 could resideoutside of TFS 146 on a memory elsewhere in IMS 106. In anotherimplementation, mobility manager 148 could reside on a memory accessibleby TFS 146 over network 114. Similarly, it will be understood that in anetworked environment, program modules and applications such as amobility manager 148 depicted and discussed above in conjunction withthe telephony feature server 146 or portions thereof, may be stored in aremote storage device. By way of example, mobility manager 148 mayreside on a memory device of a remote computer communicatively coupledto IMS 106. For purposes of illustration, application programs and otherexecutable program components—such as mobility manager 148—may reside atvarious times in different storage components of TFS 146 or of a remotecomputer, and may be executed by one of the at least one processor(s)202 of the TFS 146, or by processors on the remote computer.

In operation, signals (such as phone calls) being sent to and fromhandset 102 can trigger IMS 106, to activate TFS 146. For example, onceTFS 146 is notified that a signal addressed to handset 102 has beenreceived by PSTN 134, GSMC 126, or MGW 136, mobility manager 148 canquery a subscriber catalog 129, 137 such as might be found in homelocation register 130 and home subscriber subsystem 138, respectively,to determine the registration status of handset 102 (i.e. to see ifhandset 102 is registered on access point 110 or on wireless network104). If handset 102 is registered on access point 110, for example,mobility manager 148 and/or TFS 146 can send the signal to handset 102via a corresponding mobile switching center, network controller 132,network 114 and access point 110.

In one implementation, handset 102 may be rung to indicate the presenceof the signal. In another possible implementation, one or more of thephones associated with access point 110 (including IP phone 118 andanalog phone 120), as well as one or more analog phones in location 108connected to POTS lines, can be rung in addition to handset 102 by TFS146 and/or mobility manager 148 to enable the user to accept the signalat any of the phones.

For example, a normal phone call to handset 102 can result in theringing of all phones in location 108, including handset 102, enablingthe user to conveniently accept the call at the nearest phone to him.Alternately, the user may choose one phone in location 108, and allowanother user to choose a different phone in location 108, such that bothindividuals may interact with the incoming call, and each other, overthe chosen phones in location 108. In such a manner, user of handset 102can easily facilitate an impromptu conference call allowing severalusers to speak with each other.

In yet another possible implementation, when a call addressed to analogphone 120, IP phone 118, or a regular analog phone in location 108connected to a POTS line, is received by PSTN 134, GMSC 126 or MGW 136,TFS 146 and/or mobility manager 148 may cause handset 102 to ring inaddition to the phone to which the call is addressed (and other phonesif desired by user).

In all of these examples mentioned above, the phones which ring inresponse to a received signal can be preprogrammed into the TFS 140and/or the mobility manager 148 in any desired configuration. Thus, asignal intended for a teenager's cell phone registered on access point110 may only result in the teenager's handset being rung, while a signaladdressed to a parent's handset registered on access point 110 mayresult in the parent's handset and phones in, for example, a bedroom andhome office to ring.

Also, if in response to the rings no phone is activated, the signal mayeither activate an answering machine in one or more of the phones 118,120 in location 108, or the signal may be routed to voicemail featureserver 144.

In another possible implementation, if handset 102 is registered onaccess point 110 and a signal is sent from handset 102, the signal issent via access point over network 114 to network controller 132. If thesignal is addressed to a phone connected to a POTS line, the signal canbe routed to PSTN 134 via GMSC 126 and MSC 128 by network controller132. Alternately, if the signal is addressed to a mobile phone, such acellular phone, the signal may be routed to a base station controllerthrough which the mobile phone may be reached via a corresponding mobileswitching center.

If however, the signal is from a handset registered to an access point,like access point 110, the signal can be sent from controller 132, toIMS 106 via MSC 128 and GMSC 126. The particular access point on whichthe destination handset is registered can then be found by the TFS 146and/or mobility manager 148, and the signal can be sent to thedestination handset in a manner similar that described above.

As previously described, signals can be voiced communications, such asphone calls, or text based messages such as instant messages. In onepossible implementation, a client for instant messaging may reside onhandset 102, enabling handset 102 to send and receive instant messagesaddressed to computer 116 when handset 102 is registered on access point110. In such a manner, a user may free up computer 116 for other useswhile still retaining the ability to communicate via instant messagesusing handset 102.

When handset 102 is not registered on access point 110, and instead isregistered on wireless network 104, a signal intended for handset 102received by PSTN 134, GSMC 126, or MGW 136 can activate TFS 146 in asimilar manner. For example, mobility manager 148 can query a subscribercatalog 129, 137 such as might be found in home location register 130and home subscriber subsystem 138, respectively, to determine theregistration status of handset 102 (i.e. to see if handset 102 isregistered on access point 110 or on wireless network 104). When it isdetermined that handset 102 is not registered on access point 110,mobility manager 148 and/or TFS 146 can send the signal to a propermobile switching center (MSC 128) such that the signal may betransmitted to handset 102 via a corresponding base station controller(BSC 124) and cell tower 112.

Sending a Signal to a Handset

FIG. 3 illustrates an exemplary method 300 of sending a signal to ahandset. For ease of understanding, the method 300 is delineated asseparate steps represented as independent blocks in FIG. 3; however,these separately delineated steps should not be construed as necessarilyorder dependent in their performance. Moreover, it is also possible thatone or more of the provided steps may be omitted. Additionally, fordiscussion purposes only, the method 300 is described with reference toelements in FIGS. 1-2. However, it is understood that the method 300 maybe performed, at least in part, by elements other than those shown inFIGS. 1-2 without departing from the spirit and scope of the subjectmatter described herein.

At block 302, a signal intended for handset 102 is received. As notedabove, the received signal can include text or voice-based informationas well as commands and instructions. To facilitate delivery of thesignal, the status of registration of handset 102 is established (block304). In one possible implementation, this may be done by querying asubscriber catalog 129, 137 such as might be found in home locationregister 130 and home subscriber subsystem 138, respectively. If handset102 is turned on and communicating, the registration status of handset102 can provide information as to whether handset 102 is registered onwireless network 104 or access point 110. If it is found that handset102 is registered to wireless network 104 (‘yes’ path from block 306)then the signal is sent to handset 102 via wireless network 104 (block308).

If however, handset 102 is not registered on wireless network 104 (‘no’path from block 306), but instead handset 102 is registered on accesspoint 110 (‘yes’ path from block 310), then the signal can be sent tohandset 102 via network 114 and access point 110 (block 312). Fromaccess point 110 to handset 102, the signal may be sent using a radiotechnology, including Wi-Fi technology.

Alternately, if handset 102 is not registered on access point 110 (‘no’path from block 310), the signal can be sent to a voicemail server suchas voicemail feature server 144 (block 314).

It will also be understood that some of the above mentioned blocks maybe combined. For example blocks 306 and 310 may be combined into onedecision block. In such a decision block, if handset 102 is found to beregistered to wireless network 104, the signal can be sent to handset102 via wireless network 104. Conversely, if handset 102 is found to beregistered on access point 110, then the signal can be sent to handset102 via network 114 and access point 110. If, however, handset 102 isfound to be registered on neither wireless network 104 nor access point110, the signal can be sent to a voicemail server.

Method of Activating Multiple Phones

FIG. 4 illustrates an exemplary method 400 of activating multiple phonesin response to a signal intended for a handset registered on an accesspoint 110. For ease of understanding, the method 400 is delineated asseparate steps represented as independent blocks in FIG. 4; however,these separately delineated steps should not be construed as necessarilyorder dependent in their performance. Moreover, it is also possible thatone or more of the provided steps may be omitted. Additionally, fordiscussion purposes, the method 400 is described with reference toelements in FIGS. 1-2. However, it is understood that the method 400 maybe performed, at least in part, by elements other than those shown inFIGS. 1-2 without departing from the spirit and scope of the subjectmatter described herein.

In one exemplary implementation, the registration status of handset isviewed and it is determined that handset 102 is registered on accesspoint 110 (block (402). A received signal intended for handset 102(block 404) can then be routed to handset 102 using the registrationstatus of handset 102. In addition to routing the signal to handset 102,the signal may also be routed to all other phones associated with theaccess point 110 on which handset 102 is registered (block 404) thusactivating these additional phones. In the instance that the receivedsignal is a phone call, handset 102, and one or more phones associatedwith access point 110, for example, IP phone 118 and analog phone 120,may be rung. Additionally, any analog phones connected to POTS lineswhich are in the proximity of access point 110 may be rung. In thismatter a user of handset 102 may choose to receive the signal on handset102 or any of the other phones which are rung in response to the signal.In other possible implementations, the signal may include text-basedinformation and/or commands and instructions. Moreover, a user maypreset just which phones are rung in response to the signal intended forhandset 102 according to the user's preferences and/or needs.

Method of Activating Handset When Handset Registered on Access Point

FIG. 5 illustrates another exemplary method 500 of activating multiplephones when handset 102 is registered on access point 110. For ease ofunderstanding, the method 500 is delineated as separate stepsrepresented as independent blocks in FIG. 5; however, these separatelydelineated steps should not be construed as necessarily order dependentin their performance. Moreover, it is also possible that one or more ofthe provided steps may be omitted. Additionally, for discussionpurposes, the method 500 is described with reference to elements inFIGS. 1-2. However, it is understood that the method 500 may beperformed, at least in part, by elements other than those shown in FIGS.1-2 without departing from the spirit and scope of the subject matterdescribed herein.

In one exemplary implementation, the registration status of handset isviewed and it is determined that handset 102 is registered on accesspoint 110 (block 502). If a signal is received with is intended for aphone associated with access point 110, such as, for example, IP phone118 or analog phone 120 (block 504), the signal can be routed to theintended phone as well as handset 102 and any other desired phonesassociated with access point, including analog phones in the vicinity ofaccess point 110 which are coupled to POTS lines (block 508). In theinstance that the received signal is a phone call, handset 102, theintended phone, and one or more of the remaining phones associated withthe access point 110 may be rung. In this manner a user of handset 102may choose to receive the signal on handset 102, the intended phone, orany of the other phones which are rung in response to the signal. Inother possible implementations, the signal may include text-basedinformation and/or commands and instructions. Moreover, just whichphones are rung in response to the signal may be preset according to theuser's preferences and/or needs.

Sending a Signal from a Handset

FIG. 6 illustrates an exemplary method 600 of sending a signal from ahandset. For ease of understanding, the method 600 is delineated asseparate steps represented as independent blocks if FIG. 6; however,these separately delineated steps should be construed as necessarilyorder dependent in their performance. Moreover, it is also possible thatone or more of the provided steps may be omitted. Additionally, fordiscussion purposes, the method 600 is described with reference toelements in FIGS. 1-2. However, it is understood that the method 600 maybe performed, at least in party, by elements other than those shown inFIGS. 1-2 without departing from the spirit and scope of the subjectmatter described herein.

At block 602, a signal being transmitted from handset 102 is detected.As noted above, the transmitted signal can include text or voice-basedinformation as well as commands and instructions. To facilitate deliveryof the signal, the status of registration of handset 102 is established(block 604). In one possible implementation, this may be done byquerying a subscriber catalog 129, 137 such as might be found in homelocation register 130 and home subscriber subsystem 138, respectively.If handset 102 is turned on and communicating, the registration statusof handset 102 can provide information as to whether handset 102 isregistered on wireless network 104 or access point 110.

If is found that handset 102 is registered to wireless network 104(‘yes’ path from block 606) then the signal is sent from handset 102 towireless network 104 (block 608).

If, however, handset 102 is not registered on wireless network 104 (‘no’path from block 606), but instead handset 102 is registered on accesspoint 110 (‘yes’ path from block 610), then the signal can be sent fromhandset 102 via network 114 and access point 110 (‘yes’ path from block610). From handset 102 to access point 110, the signal may be sent usinga radio technology, including Wi-Fi technology.

Alternately, if handset 102 is not registered on access point 110 (‘no’path from block 610), an error message may be displayed on handset 102telling the user that the signal cannot be sent (block 614).

As noted above, some of the above mentioned blocks may be omitted. Forexample, in one exemplary implementation block 604 may be omitted, andinstead once an attempt is made to transmit a signal from handset 102,whichever of access point 110 or wireless network 104 handset 102 isregistered on may automatically send the signal over it's correspondingnetwork (i.e. network 114 or wireless network 104) or print an errormessage as shown in blocks 606-614.

It will also be understood that some of the above-mention blocks may becombined. For example, blocks 606 and 610 may be combined into onedecision block. In such a decision block, if handset 102 is found to beregistered on wireless network 104, the signal can be sent from handset102 to wireless network 104. Conversely, if handset 102 is found to beregistered on access point 110, then the signal can be sent from handset102 via network 114 and access point 110. If however, handset 102 iffound to be registered on neither wireless network 104 nor access point110, the signal cannot be sent, and an error message can be presented tothe user of handset 102.

CONCLUSION

Although exemplary embodiments have been described in language specificto structural features and/or methodological acts, it is to beunderstood that the invention is not necessarily limited to the specificfeatures or acts described. Rather, the specific features and acts aredisclosed as exemplary forms of implementing the invention.

1. A method, performed by a mobility manager of a remote server, theremote server being distinct from a first device and a second device,the method comprising: generating, at the mobility manager of the remoteserver, a request for a registration status of the first device and thesecond device, the first device and the second device being separatefrom each other and from the remote server; sending, from the mobilitymanager of the remote server, the request for the registration status ofthe first device and the second device to a wireless access point;receiving, at the mobility manager of the remote server, registrationstatuses from the wireless access point, and receiving the statusesindicating that both the first and second devices are registered withthe wireless access point, the registration statuses indicating that thefirst device and the second device are registered with the wirelessaccess point; and responsive to receiving a communication addressed toat least one of the first device and the second device, the mobilitymanager of the remote server sending the communication to the wirelessaccess point for routing by the wireless access point to both the firstdevice and the second device.
 2. The method of claim 1, whereingenerating the request for the registration status of the first deviceand the second device comprises generating the request for theregistration status of the first device and the second device, whereineach of the first device and the second device is a device selected froma group of devices consisting of: a plain old telephone system phone; aninternet protocol phone; a wireless handset; a computer; a computingdevice; a handheld video game device; and a personal digital assistant.3. The method of claim 1, further comprising providing the registrationstatus to a home subscription subsystem.
 4. The method of claim 1,further comprising providing the registration status to a home locationregister.
 5. The method of claim 1, wherein sending the request to awireless access point, receiving the registration status from thewireless access point, and sending the communication to the wirelessaccess point are all effected via an internet protocol wide areanetwork.
 6. The method of claim 1, wherein sending the request to awireless access point, receiving the registration status from thewireless access point, and sending the communication to the wirelessaccess point are all effected via the Internet.
 7. The method of claim1, wherein the mobility manager is located in an internet protocolmultimedia subsystem network.
 8. The method of claim 1, wherein sendingthe communication to the wireless access point for routing by thewireless access point to the first device and to the second devicecomprises sending a communication selected from a group ofcommunications consisting of a voice communication, a phone call, atext-based communication, and an instant message.
 9. A tangiblecomputer-readable storage medium comprising computer-executableinstructions that, when executed by a processor, cause the processor toperform a method comprising: generating a request for a registrationstatus of a first device and a second device, the first device and thesecond device being separate from each other and separate from thecomputer-readable storage medium; sending the request for theregistration status of the first device and the second device to awireless access point; receiving registration statuses from the wirelessaccess point, the registration statuses indicating that the first deviceand the second device are registered with the wireless access point; andresponsive to receiving a communication addressed to at least one of thefirst device and the second device, and receiving the statusesindicating that both the first and second devices are registered withthe wireless access point, sending the communication to the wirelessaccess point for routing by the wireless access point to both the firstdevice and the second device.
 10. The tangible computer-readable storagemedium of claim 9, wherein the instructions for generating the requestfor the registration status of the first device and the second devicecomprise instructions for generating the request for the registrationstatus of the first device and the second device, wherein each of thefirst device and the second device is a device selected from a group ofdevices consisting of: a plain old telephone system phone; an internetprotocol phone; a wireless handset; a computer; a computing device; ahandheld video game device; and a personal digital assistant.
 11. Thetangible computer-readable storage medium of claim 9, further comprisinginstructions that, when executed by the processor, cause the processorto perform the method further comprising providing the registrationstatus to a home subscription subsystem.
 12. The tangiblecomputer-readable storage medium of claim 9, further comprisinginstructions that, when executed by the processor, cause the processorto perform the method further comprising providing the registrationstatus to a home location register.
 13. The tangible computer-readablestorage medium of claim 9, wherein the instructions for sending thecommunication to the wireless access point for routing by the wirelessaccess point to the first device and the second device compriseinstructions for sending a communication selected from a group ofcommunications consisting of a voice communication, a phone call, atext-based communication, and an instant message.
 14. A remote servercomprising: a network interface; a processor in communication with thenetwork interface; a memory in communication with the processor, thememory comprising instructions executable by the processor to: generatea request for a registration status of a first device and a seconddevice, the first device and the second device being separate from eachother and separate from the remote server; send, via the networkinterface, the request for the registration status of the first deviceand the second device to a wireless access point; receive, via thenetwork interface, registration statuses from the wireless access point,the registration statuses indicating that the first device and thesecond device are registered with the wireless access point; andresponsive to receiving, via the network interface, a communicationaddressed to at least one of the first device and the second device, andreceiving the statuses indicating that both the first and second devicesare registered with the wireless access point, send the communication tothe wireless access point for routing by the wireless access point toboth the first device and the second device.
 15. The server of claim 14,wherein the instructions executable by the processor to generate therequest for the registration status of the first device and the seconddevice comprise instructions executable by the processor to generate therequest for the registration status of the first device and the seconddevice, wherein each of the first device and the second device is adevice selected from a group of devices consisting of: a plain oldtelephone system phone; an internet protocol phone; a wireless handset;a computer; a computing device; a handheld video game device; and apersonal digital assistant.
 16. The server of claim 14, wherein thememory further comprises instructions executable by the processor toprovide the registration status to a home subscription subsystem. 17.The server of claim 14, wherein the memory further comprisesinstructions executable by the processor to provide the registrationstatus to a home location register.
 18. The server of claim 14, whereinthe instructions executable by the processor to send the communicationto the wireless access point for routing by the wireless access point tothe first device and the second device comprise instructions executableby the processor to send a communication selected from a group ofcommunications consisting of a voice communication, a phone call, atext-based communication, and an instant message.
 19. The server ofclaim 14, wherein the instructions executable by the processor to send,via the network interface, the request to a wireless access point,receive, via the network interface, the registration status from thewireless access point, and send, via the network interface, thecommunication to the wireless access point by way of an internetprotocol wide area network.
 20. The server of claim 14, wherein theinstructions executable by the processor to send, via the networkinterface, the request to a wireless access point, receive, via thenetwork interface, the registration status from the wireless accesspoint, and send, via the network interface, the communication to thewireless access point by way of the Internet.